Skip to content

[Backend] claimable.service.ts cache key does not include token addre… - #1075

Open
BigMick03 wants to merge 3 commits into
LabsCrypt:mainfrom
BigMick03:Flowfi
Open

[Backend] claimable.service.ts cache key does not include token addre…#1075
BigMick03 wants to merge 3 commits into
LabsCrypt:mainfrom
BigMick03:Flowfi

Conversation

@BigMick03

Copy link
Copy Markdown

…ss, so streams with the same id across tokens could collide

Description

Type of Change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📚 Documentation update
  • 🔧 Refactoring (no functional changes)
  • ⚡ Performance improvement
  • 🧪 Test addition or update

Related Issues

Closes #1021

Changes Made

Testing

Test Coverage

  • Unit tests added/updated
  • Integration tests added/updated
  • Manual testing performed

Test Steps

Breaking Changes

Breaking Changes:

Migration Guide:

Screenshots/Demo

Checklist

  • My code follows the project's style guidelines
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published
  • I have checked for breaking changes and documented them if applicable

Additional Notes

@ogazboiz ogazboiz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the cross-token cache test is nice and the defensive intent is fine (streamId is @unique so the practical risk is low). one real blocker:

  1. the service uses stream.tokenAddress but ClaimableStreamState (claimable.service.ts:6-18) never gains a tokenAddress field, which is a TS2339 compile error currently masked by the earlier npm ci failure. add tokenAddress: string to the interface and the result select typing.
  2. fill in the PR template body.
  3. rebase and re-run now that main is green again.

if you want to keep contributing, join us on Telegram: https://t.me/+DOylgFv1jyJlNzM0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Backend] claimable.service.ts cache key does not include token address, so streams with the same id across tokens could collide

2 participants